Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7679311d3c08680a1dd9fac62aa9450dc4b7d19f38dcad155777aa5a1b5ae7a5

Tx prefix hash: 7adcc435032bb9ecf21f46ebf7061907a5a2856654f859d86f7ee6a45a3a58da
Tx public key: 72b62ca58442521870c623dba0158723e98ae6e93c4d1cda6200d982abc7dcb8
Timestamp: 1744175199 Timestamp [UCT]: 2025-04-09 05:06:39 Age [y:d:h:m:s]: 00:273:09:56:18
Block: 1257475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193219 RingCT/type: yes/0
Extra: 0172b62ca58442521870c623dba0158723e98ae6e93c4d1cda6200d982abc7dcb80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2ea6f208c2505958c24b440b966dcec88aacbf13d33eebeef58440cf8b4e6b7 0.600000000000 1744598 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": 1257485, "vin": [ { "gen": { "height": 1257475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2ea6f208c2505958c24b440b966dcec88aacbf13d33eebeef58440cf8b4e6b7" } } ], "extra": [ 1, 114, 182, 44, 165, 132, 66, 82, 24, 112, 198, 35, 219, 160, 21, 135, 35, 233, 138, 230, 233, 60, 77, 28, 218, 98, 0, 217, 130, 171, 199, 220, 184, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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