Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2668613797e0bd9a6efcb4af285996a6acdbd8547b915f0f97471188ec53de66

Tx prefix hash: a21b0296a7b13695fd18b81e80cdff4e012acc164a001cc5925f25f5dbcff16b
Tx public key: f462271723a61f9437f515a93b6a66fec92bb472c759859fce62c038fd7fb4e9
Timestamp: 1716884742 Timestamp [UCT]: 2024-05-28 08:25:42 Age [y:d:h:m:s]: 00:289:02:33:25
Block: 1031737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206625 RingCT/type: yes/0
Extra: 01f462271723a61f9437f515a93b6a66fec92bb472c759859fce62c038fd7fb4e90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db0dd517b4184ce3e8ba6018bffaf3ae3f2828e0c591ea0fd4c7d101846809ac 0.600000000000 1500186 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": 1031747, "vin": [ { "gen": { "height": 1031737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db0dd517b4184ce3e8ba6018bffaf3ae3f2828e0c591ea0fd4c7d101846809ac" } } ], "extra": [ 1, 244, 98, 39, 23, 35, 166, 31, 148, 55, 245, 21, 169, 59, 106, 102, 254, 201, 43, 180, 114, 199, 89, 133, 159, 206, 98, 192, 56, 253, 127, 180, 233, 2, 17, 0, 0, 0, 3, 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