Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b700c98e37068b367d6c03a2e1bca8b689afa010bf433d50cb00e43733935b55

Tx prefix hash: 6e186dd297e3d73ea7abeac829125da2e02df870c50bea142cf71b89f4264ba3
Tx public key: 009a086758e5cb28d6498c7f6e759ba5bcf54f4fd09387fdc03267b7d58711d0
Timestamp: 1729944920 Timestamp [UCT]: 2024-10-26 12:15:20 Age [y:d:h:m:s]: 00:028:19:51:30
Block: 1139969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20586 RingCT/type: yes/0
Extra: 01009a086758e5cb28d6498c7f6e759ba5bcf54f4fd09387fdc03267b7d58711d0021100000005a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e233c6304a2f88b5c00228d404e61524e1344dce434c65db6ec336a24bba437 0.600000000000 1623756 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": 1139979, "vin": [ { "gen": { "height": 1139969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e233c6304a2f88b5c00228d404e61524e1344dce434c65db6ec336a24bba437" } } ], "extra": [ 1, 0, 154, 8, 103, 88, 229, 203, 40, 214, 73, 140, 127, 110, 117, 155, 165, 188, 245, 79, 79, 208, 147, 135, 253, 192, 50, 103, 183, 213, 135, 17, 208, 2, 17, 0, 0, 0, 5, 161, 29, 186, 152, 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