Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71b60fef02a7cf1edc0b8c069e8bc2f6f12da34bc1181a1dbda60a6bbdd66124

Tx prefix hash: 5dd055bb312e941ec068797971222d71d283d7c4e3d216e8c54c51ed8aa9a921
Tx public key: 8d8184f492c4cfd98be7612fda2e4427f5f05517a364b166a044306bc60441f6
Timestamp: 1738161228 Timestamp [UCT]: 2025-01-29 14:33:48 Age [y:d:h:m:s]: 00:139:06:17:01
Block: 1207701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99480 RingCT/type: yes/0
Extra: 018d8184f492c4cfd98be7612fda2e4427f5f05517a364b166a044306bc60441f60211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb05eaa6af1a9964b8d6be3492d94d903f7988587316eacf142ed5a326ef4124 0.600000000000 1694426 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": 1207711, "vin": [ { "gen": { "height": 1207701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb05eaa6af1a9964b8d6be3492d94d903f7988587316eacf142ed5a326ef4124" } } ], "extra": [ 1, 141, 129, 132, 244, 146, 196, 207, 217, 139, 231, 97, 47, 218, 46, 68, 39, 245, 240, 85, 23, 163, 100, 177, 102, 160, 68, 48, 107, 198, 4, 65, 246, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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