Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6215ade8a4e3ee8f18e39bfa0932bf2bb757c4d33aa03e516b43da42f5135279

Tx prefix hash: 02d82ff0b52846fcbda3e28beaff2e69b8c549e2d1ee5e11e4ed2f2bc5aca554
Tx public key: ed465aa9ba38f20d1c8e9a13477fdd2d37447850eb2c628a26e3b3bb091474cf
Timestamp: 1660456848 Timestamp [UCT]: 2022-08-14 06:00:48 Age [y:d:h:m:s]: 03:086:12:39:59
Block: 565466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 841651 RingCT/type: yes/0
Extra: 01ed465aa9ba38f20d1c8e9a13477fdd2d37447850eb2c628a26e3b3bb091474cf021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.210630639000 dcy

stealth address amount amount idx
00: 9da0f11f261d4ae2179c32d5108c603509b0ce1fe4f3b1d6e8cb8a813aee6883 8.210630639000 998368 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": 565476, "vin": [ { "gen": { "height": 565466 } } ], "vout": [ { "amount": 8210630639, "target": { "key": "9da0f11f261d4ae2179c32d5108c603509b0ce1fe4f3b1d6e8cb8a813aee6883" } } ], "extra": [ 1, 237, 70, 90, 169, 186, 56, 242, 13, 28, 142, 154, 19, 71, 127, 221, 45, 55, 68, 120, 80, 235, 44, 98, 138, 38, 227, 179, 187, 9, 20, 116, 207, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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