Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa385a6a192aacacb510474570d430e2e703943c0955b9b2314af29d4caf442

Tx prefix hash: 19c84314e0eb20320f211aecf66234982b9cea838bc62a9ebd04f04df9f3aacd
Tx public key: b91a011fdfff17dd0486e5c6198fe10bb170741ef2c1258070227c4afdfd5de3
Timestamp: 1577017859 Timestamp [UCT]: 2019-12-22 12:30:59 Age [y:d:h:m:s]: 04:320:06:58:27
Block: 29627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117664 RingCT/type: yes/0
Extra: 01b91a011fdfff17dd0486e5c6198fe10bb170741ef2c1258070227c4afdfd5de30211000000274943cd9f000000000000000000

1 output(s) for total of 489.592000354000 dcy

stealth address amount amount idx
00: 332ec80319c831e4d9373bf2e9319d870b68f5d5ac0819d823f679f18bda30e7 489.592000354000 48747 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": 29637, "vin": [ { "gen": { "height": 29627 } } ], "vout": [ { "amount": 489592000354, "target": { "key": "332ec80319c831e4d9373bf2e9319d870b68f5d5ac0819d823f679f18bda30e7" } } ], "extra": [ 1, 185, 26, 1, 31, 223, 255, 23, 221, 4, 134, 229, 198, 25, 143, 225, 11, 177, 112, 116, 30, 242, 193, 37, 128, 112, 34, 124, 74, 253, 253, 93, 227, 2, 17, 0, 0, 0, 39, 73, 67, 205, 159, 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