Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b09d15d1e0b699985da7bd53b98f8730777945adcf55cf597f7e038af622c8ec

Tx prefix hash: 0bbc8291ebb5dd675dcf3f24c2fc488b9b29ca21e6fd504812d5dd46a624077a
Tx public key: df443394fbbb3fbd6ccecfdc58078a9f3b469a760ab9c2d5c36829f59ba8cbe9
Timestamp: 1710854477 Timestamp [UCT]: 2024-03-19 13:21:17 Age [y:d:h:m:s]: 01:231:16:36:36
Block: 981753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424259 RingCT/type: yes/0
Extra: 01df443394fbbb3fbd6ccecfdc58078a9f3b469a760ab9c2d5c36829f59ba8cbe9021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 989f4f81081a2292509c6d855406e7e8a1597b8d7939913496e8acacaacaf462 0.600000000000 1441850 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": 981763, "vin": [ { "gen": { "height": 981753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "989f4f81081a2292509c6d855406e7e8a1597b8d7939913496e8acacaacaf462" } } ], "extra": [ 1, 223, 68, 51, 148, 251, 187, 63, 189, 108, 206, 207, 220, 88, 7, 138, 159, 59, 70, 154, 118, 10, 185, 194, 213, 195, 104, 41, 245, 155, 168, 203, 233, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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