Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17817ce1d44d15b5502f2e45f6ad9ff4b3e7f29c47e2bda9eb8ce1732e66fba7

Tx prefix hash: d5f652dd49672484b773e218bfe13abe6d53bee3c04fa9fef1ec7d6d8daa6709
Tx public key: 9701631064a1d8800e21c3c83b2d1a4a63f1924521834ce2f26c69ec5bdce524
Timestamp: 1703785293 Timestamp [UCT]: 2023-12-28 17:41:33 Age [y:d:h:m:s]: 01:100:19:17:29
Block: 923127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333148 RingCT/type: yes/0
Extra: 019701631064a1d8800e21c3c83b2d1a4a63f1924521834ce2f26c69ec5bdce52402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 325e7a98498a4e8842f64fcf3601f8cb7dd511e8158d199270191265c07a0b58 0.600000000000 1380845 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": 923137, "vin": [ { "gen": { "height": 923127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "325e7a98498a4e8842f64fcf3601f8cb7dd511e8158d199270191265c07a0b58" } } ], "extra": [ 1, 151, 1, 99, 16, 100, 161, 216, 128, 14, 33, 195, 200, 59, 45, 26, 74, 99, 241, 146, 69, 33, 131, 76, 226, 242, 108, 105, 236, 91, 220, 229, 36, 2, 17, 0, 0, 0, 1, 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