Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bde1377df1b08fbcc9c115aa8df2603b768155f4f7d5f22fff6fa340796caee9

Tx prefix hash: 00808f7b6e8dd2325116e48441ec6cd5d96decec3d6e87e355017de7be620a40
Tx public key: 060fbb2fbc81e692633bd1ee88b5775461f351d1b6c1e1a0a157f5461b6e3638
Timestamp: 1702437549 Timestamp [UCT]: 2023-12-13 03:19:09 Age [y:d:h:m:s]: 01:116:03:38:55
Block: 911971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344130 RingCT/type: yes/0
Extra: 01060fbb2fbc81e692633bd1ee88b5775461f351d1b6c1e1a0a157f5461b6e3638021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f81395ff1430c371c78105a13a75b29141f04078f716ac39a7bbbd0b7faa4bf8 0.600000000000 1369189 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": 911981, "vin": [ { "gen": { "height": 911971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f81395ff1430c371c78105a13a75b29141f04078f716ac39a7bbbd0b7faa4bf8" } } ], "extra": [ 1, 6, 15, 187, 47, 188, 129, 230, 146, 99, 59, 209, 238, 136, 181, 119, 84, 97, 243, 81, 209, 182, 193, 225, 160, 161, 87, 245, 70, 27, 110, 54, 56, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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