Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b27e972a9ba498b1235ac61518fefdbff9422d6febce0c815a9878dca566402

Tx prefix hash: ffa57717deaa0f06e550f8107fed0bc10b416611e9f4c648eb4fb24574f2c4e9
Tx public key: d39e449462496439bd3409021691ea0883f4bfe53760ea511e5dc8ce30e1d75c
Timestamp: 1576928535 Timestamp [UCT]: 2019-12-21 11:42:15 Age [y:d:h:m:s]: 05:047:14:54:20
Block: 29364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182979 RingCT/type: yes/0
Extra: 01d39e449462496439bd3409021691ea0883f4bfe53760ea511e5dc8ce30e1d75c02110000001b9159db1e000000000000000000

1 output(s) for total of 490.575371767000 dcy

stealth address amount amount idx
00: bfa403683fdb52a2628076a08d1165225c2819d2dcc6f9f47e704557abbdddc6 490.575371767000 48198 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": 29374, "vin": [ { "gen": { "height": 29364 } } ], "vout": [ { "amount": 490575371767, "target": { "key": "bfa403683fdb52a2628076a08d1165225c2819d2dcc6f9f47e704557abbdddc6" } } ], "extra": [ 1, 211, 158, 68, 148, 98, 73, 100, 57, 189, 52, 9, 2, 22, 145, 234, 8, 131, 244, 191, 229, 55, 96, 234, 81, 30, 93, 200, 206, 48, 225, 215, 92, 2, 17, 0, 0, 0, 27, 145, 89, 219, 30, 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