Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a6c8d8882b492686bfe073cced0c8d49bb87013c4f5a32f64c8a47ef189f5c7

Tx prefix hash: d5502ac057d86cae404055ea1bc230b9acd3bc481e43e6dafd8ba14ebf2fcf57
Tx public key: 5420d298aeeb94826142788ab1b820890061641f0c04bad34184e95edf18ed61
Timestamp: 1580968432 Timestamp [UCT]: 2020-02-06 05:53:52 Age [y:d:h:m:s]: 04:274:04:38:28
Block: 59470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087560 RingCT/type: yes/0
Extra: 015420d298aeeb94826142788ab1b820890061641f0c04bad34184e95edf18ed610211106c447f00000000000000000000000000

1 output(s) for total of 389.898910771000 dcy

stealth address amount amount idx
00: 2af31c626c78b9a52e48e1458b4efee2c3f00a01a836c106f29f3e85829865c2 389.898910771000 109845 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": 59480, "vin": [ { "gen": { "height": 59470 } } ], "vout": [ { "amount": 389898910771, "target": { "key": "2af31c626c78b9a52e48e1458b4efee2c3f00a01a836c106f29f3e85829865c2" } } ], "extra": [ 1, 84, 32, 210, 152, 174, 235, 148, 130, 97, 66, 120, 138, 177, 184, 32, 137, 0, 97, 100, 31, 12, 4, 186, 211, 65, 132, 233, 94, 223, 24, 237, 97, 2, 17, 16, 108, 68, 127, 0, 0, 0, 0, 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