Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75dd64c0bae8402e7ca9da18e8ec2b509a9fb5358f683ec6231fa249778605f3

Tx prefix hash: be7e62dec067af455545077c76154141b7e9c60ab3c33ed24dbeff9aef45a1c0
Tx public key: 4a5a1614c974365b79dac844c2bafee808f179354d90e696d5fbe7932a6bee77
Timestamp: 1700859210 Timestamp [UCT]: 2023-11-24 20:53:30 Age [y:d:h:m:s]: 01:135:04:52:53
Block: 898870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357778 RingCT/type: yes/0
Extra: 014a5a1614c974365b79dac844c2bafee808f179354d90e696d5fbe7932a6bee77021100000003faf35c9c000000000000000000

1 output(s) for total of 0.645164610000 dcy

stealth address amount amount idx
00: 72d0a20246652e9ed43a27bcaedd7b4ceb908d08fbc64919263ae7d5f4f918af 0.645164610000 1355307 of 0

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": 898880, "vin": [ { "gen": { "height": 898870 } } ], "vout": [ { "amount": 645164610, "target": { "key": "72d0a20246652e9ed43a27bcaedd7b4ceb908d08fbc64919263ae7d5f4f918af" } } ], "extra": [ 1, 74, 90, 22, 20, 201, 116, 54, 91, 121, 218, 200, 68, 194, 186, 254, 232, 8, 241, 121, 53, 77, 144, 230, 150, 213, 251, 231, 147, 42, 107, 238, 119, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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