Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1efe0feab9bb838f46c0a0cf834e0fb4ad17b9d322c03cbfe836691e74d29033

Tx prefix hash: a6bdb8e787570c2de43258a508c86f8ca5743eda80bbbfb423162c36e9397284
Tx public key: 0ba62690b1718ca7a70e183055de297fb6cfbc1ef6b0e720fdb2d9cab256eeaf
Timestamp: 1703784116 Timestamp [UCT]: 2023-12-28 17:21:56 Age [y:d:h:m:s]: 01:171:21:22:29
Block: 923118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383893 RingCT/type: yes/0
Extra: 010ba62690b1718ca7a70e183055de297fb6cfbc1ef6b0e720fdb2d9cab256eeaf02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07d7ee020d8c8b65e31f0c917c1b09caa5eb20363a96e2f7d0a0cfdaec0afa0e 0.600000000000 1380836 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": 923128, "vin": [ { "gen": { "height": 923118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07d7ee020d8c8b65e31f0c917c1b09caa5eb20363a96e2f7d0a0cfdaec0afa0e" } } ], "extra": [ 1, 11, 166, 38, 144, 177, 113, 140, 167, 167, 14, 24, 48, 85, 222, 41, 127, 182, 207, 188, 30, 246, 176, 231, 32, 253, 178, 217, 202, 178, 86, 238, 175, 2, 17, 0, 0, 0, 1, 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