Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efa718717556bbaf25cb0fdb5473391ec78774b656d8edbf141de3383e7176d4

Tx prefix hash: a79c9db6826dd15c5e160b401349e7585fb865de754adad17eb5ea9c22f0e2b6
Tx public key: 22a5b2b7f347a87c1b0fffdf7245ca2a67810eac0913832452df9f08cbfad5cc
Timestamp: 1635329380 Timestamp [UCT]: 2021-10-27 10:09:40 Age [y:d:h:m:s]: 03:061:15:53:40
Block: 361486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 822495 RingCT/type: yes/0
Extra: 0122a5b2b7f347a87c1b0fffdf7245ca2a67810eac0913832452df9f08cbfad5cc0211000001331154028c000000000000000000

1 output(s) for total of 38.926667795000 dcy

stealth address amount amount idx
00: c2cf715d21bc86fb60f40e1c72fa161e711219777795e1b797ad0c19e419a323 38.926667795000 735428 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": 361496, "vin": [ { "gen": { "height": 361486 } } ], "vout": [ { "amount": 38926667795, "target": { "key": "c2cf715d21bc86fb60f40e1c72fa161e711219777795e1b797ad0c19e419a323" } } ], "extra": [ 1, 34, 165, 178, 183, 243, 71, 168, 124, 27, 15, 255, 223, 114, 69, 202, 42, 103, 129, 14, 172, 9, 19, 131, 36, 82, 223, 159, 8, 203, 250, 213, 204, 2, 17, 0, 0, 1, 51, 17, 84, 2, 140, 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