Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02a7a8707c532e72766754298a49be29f33e1f0ec3451e0a63d741c27339dd1e

Tx prefix hash: ce93b0f6a0b81f2f0cf4988c5f81c48d4fa48f53d7f293f9688c9b8c930e0ed4
Tx public key: fbcd790d80de6ec67624f182d0b3e61d42e1e1429093ee5648107472013d40a2
Timestamp: 1710807783 Timestamp [UCT]: 2024-03-19 00:23:03 Age [y:d:h:m:s]: 01:029:02:13:14
Block: 981364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281761 RingCT/type: yes/0
Extra: 01fbcd790d80de6ec67624f182d0b3e61d42e1e1429093ee5648107472013d40a202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a83a5028e1c46a7454413c5c47513aff62521a224c06a3e676d3d5ea7177784 0.600000000000 1441459 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": 981374, "vin": [ { "gen": { "height": 981364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a83a5028e1c46a7454413c5c47513aff62521a224c06a3e676d3d5ea7177784" } } ], "extra": [ 1, 251, 205, 121, 13, 128, 222, 110, 198, 118, 36, 241, 130, 208, 179, 230, 29, 66, 225, 225, 66, 144, 147, 238, 86, 72, 16, 116, 114, 1, 61, 64, 162, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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