Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d77a1baa0753ae17dfb8794cbe3b6c59168ac55b91d4b9965a21e901b7327585

Tx prefix hash: 6c7eb9b88943db7d33d6d7a52e5b994c05accc10e737d2616a04ee659d39002a
Tx public key: 35262804769a779ce3c5017ea1e6829cfcb026fa4788a3928c0f4b738501da14
Timestamp: 1648588764 Timestamp [UCT]: 2022-03-29 21:19:24 Age [y:d:h:m:s]: 02:246:13:10:46
Block: 469135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695788 RingCT/type: yes/0
Extra: 0135262804769a779ce3c5017ea1e6829cfcb026fa4788a3928c0f4b738501da14021100000003a8c141c5000000000000000000

1 output(s) for total of 17.122566349000 dcy

stealth address amount amount idx
00: 4aff015489081a9a910ab53d6da3c0464d343f18b2036d4fc1736d47de4e9ec1 17.122566349000 888017 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": 469145, "vin": [ { "gen": { "height": 469135 } } ], "vout": [ { "amount": 17122566349, "target": { "key": "4aff015489081a9a910ab53d6da3c0464d343f18b2036d4fc1736d47de4e9ec1" } } ], "extra": [ 1, 53, 38, 40, 4, 118, 154, 119, 156, 227, 197, 1, 126, 161, 230, 130, 156, 252, 176, 38, 250, 71, 136, 163, 146, 140, 15, 75, 115, 133, 1, 218, 20, 2, 17, 0, 0, 0, 3, 168, 193, 65, 197, 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