Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6fbd361c46122065fd35e46a500c6621bb6e13b6700a912d0634fed4cbca35

Tx prefix hash: 7449c52281dc27a7e7bbe86a631ede059307cde691ffd9129b24f18a057d7635
Tx public key: 8be68a9a4df646a16dbf17462bef84feca7f18fedf6c98cf3c8d10b0115f9c0a
Timestamp: 1723937778 Timestamp [UCT]: 2024-08-17 23:36:18 Age [y:d:h:m:s]: 00:242:04:23:13
Block: 1090200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172966 RingCT/type: yes/0
Extra: 018be68a9a4df646a16dbf17462bef84feca7f18fedf6c98cf3c8d10b0115f9c0a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47b1759d3e6c5ca25ebcfaf1fd992103271390bf2f464d7b70b333bb177238ae 0.600000000000 1564823 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": 1090210, "vin": [ { "gen": { "height": 1090200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47b1759d3e6c5ca25ebcfaf1fd992103271390bf2f464d7b70b333bb177238ae" } } ], "extra": [ 1, 139, 230, 138, 154, 77, 246, 70, 161, 109, 191, 23, 70, 43, 239, 132, 254, 202, 127, 24, 254, 223, 108, 152, 207, 60, 141, 16, 176, 17, 95, 156, 10, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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