Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6621c533cdfc7ee6d4aaebee1c78c11e74e3af2eb215155d86fec3db14adc8c4

Tx prefix hash: 166e30c91e558041a3bbf747771015b71b2c5fc0383f83f8b49177edc19168e3
Tx public key: 82562eaeec3033a1d75eb107f8c88471c0bf1ccacd619ba1b4b9368e9c61e114
Timestamp: 1580486080 Timestamp [UCT]: 2020-01-31 15:54:40 Age [y:d:h:m:s]: 05:252:09:43:52
Block: 55964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1329879 RingCT/type: yes/0
Extra: 0182562eaeec3033a1d75eb107f8c88471c0bf1ccacd619ba1b4b9368e9c61e1140211000000012264afe6000000000000000000

1 output(s) for total of 400.468960502000 dcy

stealth address amount amount idx
00: 202fe395b5becb62912acec953ea89472246ca181cfc5063bd8c3df23f53d790 400.468960502000 103213 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": 55974, "vin": [ { "gen": { "height": 55964 } } ], "vout": [ { "amount": 400468960502, "target": { "key": "202fe395b5becb62912acec953ea89472246ca181cfc5063bd8c3df23f53d790" } } ], "extra": [ 1, 130, 86, 46, 174, 236, 48, 51, 161, 215, 94, 177, 7, 248, 200, 132, 113, 192, 191, 28, 202, 205, 97, 155, 161, 180, 185, 54, 142, 156, 97, 225, 20, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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