Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81c17b0adcee25dd7b436e2a4f3f4fc532e62fc1a1aa37dfccf3d173bd01c8b6

Tx prefix hash: 5452a6fb035336c204451c6b8de9b67f2bf472ee93df03d1d13fc3e4cedeee3d
Tx public key: 9c4afdfbcd51c5fdcaba7020f8ce858117103282167fbb184f1fbe92dd9a623f
Timestamp: 1644790144 Timestamp [UCT]: 2022-02-13 22:09:04 Age [y:d:h:m:s]: 02:359:17:05:06
Block: 438004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776157 RingCT/type: yes/0
Extra: 019c4afdfbcd51c5fdcaba7020f8ce858117103282167fbb184f1fbe92dd9a623f0211000000014a0f5013000000000000000000

1 output(s) for total of 21.712569432000 dcy

stealth address amount amount idx
00: 0e0eb08f1dec645f6ab0b58c5660016cb6a754da59ed4778be28938cb6e0cbf3 21.712569432000 849783 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": 438014, "vin": [ { "gen": { "height": 438004 } } ], "vout": [ { "amount": 21712569432, "target": { "key": "0e0eb08f1dec645f6ab0b58c5660016cb6a754da59ed4778be28938cb6e0cbf3" } } ], "extra": [ 1, 156, 74, 253, 251, 205, 81, 197, 253, 202, 186, 112, 32, 248, 206, 133, 129, 23, 16, 50, 130, 22, 127, 187, 24, 79, 31, 190, 146, 221, 154, 98, 63, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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