Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc49b9abc0f977981587a6e744382b1de3237298db92403efd88fe273bb473b6

Tx prefix hash: 89e85ed0c5279909df5527f2a39bb490afd9297756d140096159926bb1b736a6
Tx public key: f812d72c64e771e5e2847e81f184de353a9bb9480d806cf07a23c8dd745d09d6
Timestamp: 1630818736 Timestamp [UCT]: 2021-09-05 05:12:16 Age [y:d:h:m:s]: 03:062:04:18:10
Block: 327736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 819260 RingCT/type: yes/0
Extra: 01f812d72c64e771e5e2847e81f184de353a9bb9480d806cf07a23c8dd745d09d6021100000014a272b9cb000000000000000000

1 output(s) for total of 50.358760507000 dcy

stealth address amount amount idx
00: 0f3519ce6fd084280bbc7030972c8b6bf4c4cff8dcd84bfd48bf4171b97713a3 50.358760507000 678653 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": 327746, "vin": [ { "gen": { "height": 327736 } } ], "vout": [ { "amount": 50358760507, "target": { "key": "0f3519ce6fd084280bbc7030972c8b6bf4c4cff8dcd84bfd48bf4171b97713a3" } } ], "extra": [ 1, 248, 18, 215, 44, 100, 231, 113, 229, 226, 132, 126, 129, 241, 132, 222, 53, 58, 155, 185, 72, 13, 128, 108, 240, 122, 35, 200, 221, 116, 93, 9, 214, 2, 17, 0, 0, 0, 20, 162, 114, 185, 203, 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