Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df3caa1516179471d90c4ca2c3fcf50363cb25d3239ab42262c031deb2c2c86a

Tx prefix hash: 1d63038b30b9e2c86dbd9c6d8a1149048a09d5a64ccae83c21ea0f17aaf283c2
Tx public key: e271ca31c3694727f8b9fb08cb45ce5190f41ae33f4ce999a68eda3a46e3d888
Timestamp: 1624480156 Timestamp [UCT]: 2021-06-23 20:29:16 Age [y:d:h:m:s]: 03:185:09:47:10
Block: 283088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899604 RingCT/type: yes/0
Extra: 01e271ca31c3694727f8b9fb08cb45ce5190f41ae33f4ce999a68eda3a46e3d88802110000016d25e03f4b000000000000000000

1 output(s) for total of 70.796608855000 dcy

stealth address amount amount idx
00: df82f96505d9006ff0563c1d967bd737aee7be6c46e64dc954da3dcb408e6e80 70.796608855000 592807 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": 283098, "vin": [ { "gen": { "height": 283088 } } ], "vout": [ { "amount": 70796608855, "target": { "key": "df82f96505d9006ff0563c1d967bd737aee7be6c46e64dc954da3dcb408e6e80" } } ], "extra": [ 1, 226, 113, 202, 49, 195, 105, 71, 39, 248, 185, 251, 8, 203, 69, 206, 81, 144, 244, 26, 227, 63, 76, 233, 153, 166, 142, 218, 58, 70, 227, 216, 136, 2, 17, 0, 0, 1, 109, 37, 224, 63, 75, 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