Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43fb6ac3667a07b76067811219a52b91396ddb9e1c3c84cd4345919f5688a1e

Tx prefix hash: 05a6a3eed52bcef9b883911fb29f25a545575e259fcc2bf60a5ef05eb5fb7e97
Tx public key: d232f04b02b033b19ed046a0726c9604fc5ce8cbd43989a448dbcc0fc07ee793
Timestamp: 1720910511 Timestamp [UCT]: 2024-07-13 22:41:51 Age [y:d:h:m:s]: 00:224:11:17:23
Block: 1065113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160313 RingCT/type: yes/0
Extra: 01d232f04b02b033b19ed046a0726c9604fc5ce8cbd43989a448dbcc0fc07ee79302110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65a876e5d529b1008684e21aa8fd92d00dd4f345fb0fb6b1ad889bc378c8e4d 0.600000000000 1535656 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": 1065123, "vin": [ { "gen": { "height": 1065113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65a876e5d529b1008684e21aa8fd92d00dd4f345fb0fb6b1ad889bc378c8e4d" } } ], "extra": [ 1, 210, 50, 240, 75, 2, 176, 51, 177, 158, 208, 70, 160, 114, 108, 150, 4, 252, 92, 232, 203, 212, 57, 137, 164, 72, 219, 204, 15, 192, 126, 231, 147, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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