Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b6b202cc416097d14e4ce0355e136193a325dcb2acbc71f078fc6bebc914bcb

Tx prefix hash: d26ad2224719c5163f15e4c611764b9dc0f16a330c026c5e3c946fe6df34fefe
Tx public key: 47724bd5deac5ee532759b6eb2e90a03bffec826a18af5b5e02689c561509794
Timestamp: 1679311056 Timestamp [UCT]: 2023-03-20 11:17:36 Age [y:d:h:m:s]: 02:234:03:05:54
Block: 721123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686579 RingCT/type: yes/0
Extra: 0147724bd5deac5ee532759b6eb2e90a03bffec826a18af5b5e02689c561509794021100000003faf35c9c000000000000000000

1 output(s) for total of 2.503917589000 dcy

stealth address amount amount idx
00: 1b319d2494cfece9440ef168059ec0f1b6087ea5f7c0d1297387d8adabde69b9 2.503917589000 1165960 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": 721133, "vin": [ { "gen": { "height": 721123 } } ], "vout": [ { "amount": 2503917589, "target": { "key": "1b319d2494cfece9440ef168059ec0f1b6087ea5f7c0d1297387d8adabde69b9" } } ], "extra": [ 1, 71, 114, 75, 213, 222, 172, 94, 229, 50, 117, 155, 110, 178, 233, 10, 3, 191, 254, 200, 38, 161, 138, 245, 181, 224, 38, 137, 197, 97, 80, 151, 148, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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