Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f086d62765583ae5a4684448c8547e60a2fd4ffd4d23d74527024fc6b78097

Tx prefix hash: 277d60db194e003bf3dc9be63cbe984209fb4359ba5f0b4091f94e3b7b65feeb
Tx public key: 6bd6da9b6f8a7859111ba963ec7b2c81865a6b7e5f935e436d8a389078da0f01
Timestamp: 1577386216 Timestamp [UCT]: 2019-12-26 18:50:16 Age [y:d:h:m:s]: 05:002:18:20:43
Block: 32399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151911 RingCT/type: yes/0
Extra: 016bd6da9b6f8a7859111ba963ec7b2c81865a6b7e5f935e436d8a389078da0f0102110000000dd81c26c0000000000000000000

1 output(s) for total of 479.346457654000 dcy

stealth address amount amount idx
00: 6f7f38eb1d5d5d4cf19fdc78c1911a8a4d85311e491db3d9967f94b87d5c40e9 479.346457654000 53864 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": 32409, "vin": [ { "gen": { "height": 32399 } } ], "vout": [ { "amount": 479346457654, "target": { "key": "6f7f38eb1d5d5d4cf19fdc78c1911a8a4d85311e491db3d9967f94b87d5c40e9" } } ], "extra": [ 1, 107, 214, 218, 155, 111, 138, 120, 89, 17, 27, 169, 99, 236, 123, 44, 129, 134, 90, 107, 126, 95, 147, 94, 67, 109, 138, 56, 144, 120, 218, 15, 1, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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