Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8657fca7698994a1567c6cb6fa9f93e2d4d739fd99669a630bbef8715cc63a8

Tx prefix hash: 0e9b75735b1b363655cca8e5a8ea5b09600d418457004f95ebffeb1f55b816cf
Tx public key: 04213f9e94b1f68e2c863c43398037d657077d2a656f761686117ce639c5e749
Timestamp: 1732851642 Timestamp [UCT]: 2024-11-29 03:40:42 Age [y:d:h:m:s]: 01:023:20:37:36
Block: 1164001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275498 RingCT/type: yes/0
Extra: 0104213f9e94b1f68e2c863c43398037d657077d2a656f761686117ce639c5e749021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fced8f5b29ca4214f2ba9cd1a39e6ad0f4afa4ee8a6c7d99c2abd0949d845a0 0.600000000000 1649672 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": 1164011, "vin": [ { "gen": { "height": 1164001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fced8f5b29ca4214f2ba9cd1a39e6ad0f4afa4ee8a6c7d99c2abd0949d845a0" } } ], "extra": [ 1, 4, 33, 63, 158, 148, 177, 246, 142, 44, 134, 60, 67, 57, 128, 55, 214, 87, 7, 125, 42, 101, 111, 118, 22, 134, 17, 124, 230, 57, 197, 231, 73, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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