Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f3f1a4ade7071c295b141a9c441f24b3e980836ccb6afcd8599880c0dbdba7c2

Tx prefix hash: d37aea9a4bebccf819fa4393ecffa8eb122a3258eac5ee794565f6bd04bfd133
Tx public key: 4306cb03dd71613d2bd0f4c448fbef659a0264c13c82660089f8230aa7d42d69
Timestamp: 1736173466 Timestamp [UCT]: 2025-01-06 14:24:26 Age [y:d:h:m:s]: 00:074:18:35:33
Block: 1191519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53209 RingCT/type: yes/0
Extra: 014306cb03dd71613d2bd0f4c448fbef659a0264c13c82660089f8230aa7d42d69021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97a99e5913ffb829a643428b0b18759d0b2e6267f6c5a1eea55b4496218e0d84 0.600000000000 1678058 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1191529, "vin": [ { "gen": { "height": 1191519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97a99e5913ffb829a643428b0b18759d0b2e6267f6c5a1eea55b4496218e0d84" } } ], "extra": [ 1, 67, 6, 203, 3, 221, 113, 97, 61, 43, 208, 244, 196, 72, 251, 239, 101, 154, 2, 100, 193, 60, 130, 102, 0, 137, 248, 35, 10, 167, 212, 45, 105, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8