Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82e8437f45615a005cc8cbf6f6d30ec9b3e2fbad16ab762c85c68b98c68a555a

Tx prefix hash: e0d9c22d4b45c984a5210e17af4d1790a52d3fb945589772c659c0a1d67df51e
Tx public key: 68d659a0af52f3814c6ba6edbe54efc83eb42ee3479dd0b7a3bf8bcc1188bc96
Timestamp: 1725724010 Timestamp [UCT]: 2024-09-07 15:46:50 Age [y:d:h:m:s]: 00:190:11:12:11
Block: 1105016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135959 RingCT/type: yes/0
Extra: 0168d659a0af52f3814c6ba6edbe54efc83eb42ee3479dd0b7a3bf8bcc1188bc96021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f79943eb212adb762f0983b6b048fb52a83c2a1dde86bea573f5a04ac0ac4274 0.600000000000 1582353 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": 1105026, "vin": [ { "gen": { "height": 1105016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f79943eb212adb762f0983b6b048fb52a83c2a1dde86bea573f5a04ac0ac4274" } } ], "extra": [ 1, 104, 214, 89, 160, 175, 82, 243, 129, 76, 107, 166, 237, 190, 84, 239, 200, 62, 180, 46, 227, 71, 157, 208, 183, 163, 191, 139, 204, 17, 136, 188, 150, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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