Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea142b13c62b9e2ea392eeff2ea83af858bb4fbb0af99c3ad3498083ab81a19

Tx prefix hash: 0bc039cf9dd5034648b0e2d9e135a2a6bc795caafc989b4706304b30ceb746b9
Tx public key: 9b56fa9e7b9dfd13bfeb1aef70bbfa1ba89dd4ece2071bee7a59f681a127e3a8
Timestamp: 1718867539 Timestamp [UCT]: 2024-06-20 07:12:19 Age [y:d:h:m:s]: 00:185:21:25:12
Block: 1048168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133065 RingCT/type: yes/0
Extra: 019b56fa9e7b9dfd13bfeb1aef70bbfa1ba89dd4ece2071bee7a59f681a127e3a802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73f5b3293cb6bfdd19eccc1e95fe7c5c8d39775de4721e54408444382372d306 0.600000000000 1518183 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": 1048178, "vin": [ { "gen": { "height": 1048168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73f5b3293cb6bfdd19eccc1e95fe7c5c8d39775de4721e54408444382372d306" } } ], "extra": [ 1, 155, 86, 250, 158, 123, 157, 253, 19, 191, 235, 26, 239, 112, 187, 250, 27, 168, 157, 212, 236, 226, 7, 27, 238, 122, 89, 246, 129, 161, 39, 227, 168, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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