Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec42c1b9d1f5fe4163a56a3e040f19823e4d77974abc60b95f2b52c08f19edd

Tx prefix hash: 4ef4489a2d98f78857a1525c1019f7ac49ba291645eb5594e630fd9ce2a169c7
Tx public key: bbba83a4ba98f5df303567f8aeff7cdfe8dbbde31e1e99154fcbbaf6d548f103
Timestamp: 1709301081 Timestamp [UCT]: 2024-03-01 13:51:21 Age [y:d:h:m:s]: 01:085:05:05:57
Block: 968868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321939 RingCT/type: yes/0
Extra: 01bbba83a4ba98f5df303567f8aeff7cdfe8dbbde31e1e99154fcbbaf6d548f1030211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38f659e6358e7c2a6fb5e1ccea06e16e550c93ed8426ecd02d393b3ebf4905f0 0.600000000000 1428691 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": 968878, "vin": [ { "gen": { "height": 968868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38f659e6358e7c2a6fb5e1ccea06e16e550c93ed8426ecd02d393b3ebf4905f0" } } ], "extra": [ 1, 187, 186, 131, 164, 186, 152, 245, 223, 48, 53, 103, 248, 174, 255, 124, 223, 232, 219, 189, 227, 30, 30, 153, 21, 79, 203, 186, 246, 213, 72, 241, 3, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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