Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0048834a663f6df5bb1f3d179927c41f8ea901797b10f7d52990f953b1d64288

Tx prefix hash: 687de31e4634a4b9f05d77958c5482391e279e365733dabfa67741e07145b320
Tx public key: 23009915d6bcc7c2fe774f6ea93ad8eb5d5148e0138e01ef4d72c1123dda05c3
Timestamp: 1733633172 Timestamp [UCT]: 2024-12-08 04:46:12 Age [y:d:h:m:s]: 00:101:13:15:34
Block: 1170479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72386 RingCT/type: yes/0
Extra: 0123009915d6bcc7c2fe774f6ea93ad8eb5d5148e0138e01ef4d72c1123dda05c3021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e78689f0579e5cb527f2d22aed33385ff51e4e5a9be5347edc1a1eef94fd57 0.600000000000 1656210 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": 1170489, "vin": [ { "gen": { "height": 1170479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e78689f0579e5cb527f2d22aed33385ff51e4e5a9be5347edc1a1eef94fd57" } } ], "extra": [ 1, 35, 0, 153, 21, 214, 188, 199, 194, 254, 119, 79, 110, 169, 58, 216, 235, 93, 81, 72, 224, 19, 142, 1, 239, 77, 114, 193, 18, 61, 218, 5, 195, 2, 17, 0, 0, 0, 5, 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