Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45144f803768d1cbcb6557897c86fdf9bec719561e93776812f1dbe1a37fd8b9

Tx prefix hash: 9eb8c39adcf7698844ea6190f9cfd97827c1733b2a40744907d215e4832bc232
Tx public key: 53deb410e72ba575c718d1f2c62c710e4d95a6a82dfb12d7b234838d039a8aa7
Timestamp: 1733628061 Timestamp [UCT]: 2024-12-08 03:21:01 Age [y:d:h:m:s]: 00:333:15:56:54
Block: 1170440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235969 RingCT/type: yes/0
Extra: 0153deb410e72ba575c718d1f2c62c710e4d95a6a82dfb12d7b234838d039a8aa702110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48e9a2d3dc17bf830518a5d3b762b34c39f2397cf3dffa50a1688a64c4e50eab 0.600000000000 1656171 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": 1170450, "vin": [ { "gen": { "height": 1170440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48e9a2d3dc17bf830518a5d3b762b34c39f2397cf3dffa50a1688a64c4e50eab" } } ], "extra": [ 1, 83, 222, 180, 16, 231, 43, 165, 117, 199, 24, 209, 242, 198, 44, 113, 14, 77, 149, 166, 168, 45, 251, 18, 215, 178, 52, 131, 141, 3, 154, 138, 167, 2, 17, 0, 0, 0, 10, 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