Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4270021b5d913d505637bdf117f3f03d583b17a5107ee99a700e9904dc4d4e2a

Tx prefix hash: 2e9a8c45f3bd4d69db1566c29141c0bb1a7dc875935eb3140f74e12d28117857
Tx public key: d666b4e6eb472026119e8f6263743acf188a7b142e57538318eada9032a413a4
Timestamp: 1686056733 Timestamp [UCT]: 2023-06-06 13:05:33 Age [y:d:h:m:s]: 01:227:17:30:57
Block: 776398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424139 RingCT/type: yes/0
Extra: 01d666b4e6eb472026119e8f6263743acf188a7b142e57538318eada9032a413a402110000000275e3f0e9000000000000000000

1 output(s) for total of 1.642371092000 dcy

stealth address amount amount idx
00: 4b0732dfe996ce3be37e31346a5145f0358b7cd39733ccfd1cd80910210e4afd 1.642371092000 1225949 of 0

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": 776408, "vin": [ { "gen": { "height": 776398 } } ], "vout": [ { "amount": 1642371092, "target": { "key": "4b0732dfe996ce3be37e31346a5145f0358b7cd39733ccfd1cd80910210e4afd" } } ], "extra": [ 1, 214, 102, 180, 230, 235, 71, 32, 38, 17, 158, 143, 98, 99, 116, 58, 207, 24, 138, 123, 20, 46, 87, 83, 131, 24, 234, 218, 144, 50, 164, 19, 164, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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