Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c44d03b9c46f4945dd949f09aba78ae54c25b725b430db2be41c47da81642cd

Tx prefix hash: 2613e0a9f870d4f0145a5f89e8221cd65905d2e971dae7b7a9a5f05e35b4fadc
Tx public key: 658816aadce22f14cd7e82e76a7e79b4f9e0418ee69243de66e12c1d0ba5994b
Timestamp: 1726300655 Timestamp [UCT]: 2024-09-14 07:57:35 Age [y:d:h:m:s]: 00:238:01:14:37
Block: 1109785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169995 RingCT/type: yes/0
Extra: 01658816aadce22f14cd7e82e76a7e79b4f9e0418ee69243de66e12c1d0ba5994b021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01b76952bba301b2216869d2b6cf5081105d7d89cafdfd3e61bf3a5b68290688 0.600000000000 1588164 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": 1109795, "vin": [ { "gen": { "height": 1109785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01b76952bba301b2216869d2b6cf5081105d7d89cafdfd3e61bf3a5b68290688" } } ], "extra": [ 1, 101, 136, 22, 170, 220, 226, 47, 20, 205, 126, 130, 231, 106, 126, 121, 180, 249, 224, 65, 142, 230, 146, 67, 222, 102, 225, 44, 29, 11, 165, 153, 75, 2, 17, 0, 0, 0, 5, 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