Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d390a2e7c664f0c4a7f44a038a67808817ac446e4daae8ac09afe8a57507b3a8

Tx prefix hash: e2a10d004e3ad1004614d51b637e543f32beabd84c7ae5b336f125e555fd34b4
Tx public key: 127b3414788e3b09fe99be35e182f06b8fdca8fc2613670555f578261164d9ac
Timestamp: 1577221734 Timestamp [UCT]: 2019-12-24 21:08:54 Age [y:d:h:m:s]: 05:070:22:58:58
Block: 31027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200436 RingCT/type: yes/0
Extra: 01127b3414788e3b09fe99be35e182f06b8fdca8fc2613670555f578261164d9ac021100000002d81c26c0000000000000000000

1 output(s) for total of 484.390402751000 dcy

stealth address amount amount idx
00: 461b267734e5f84f9f8dc7005f0a5143da23ab6234bd3416fc18a6e254227152 484.390402751000 51257 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": 31037, "vin": [ { "gen": { "height": 31027 } } ], "vout": [ { "amount": 484390402751, "target": { "key": "461b267734e5f84f9f8dc7005f0a5143da23ab6234bd3416fc18a6e254227152" } } ], "extra": [ 1, 18, 123, 52, 20, 120, 142, 59, 9, 254, 153, 190, 53, 225, 130, 240, 107, 143, 220, 168, 252, 38, 19, 103, 5, 85, 245, 120, 38, 17, 100, 217, 172, 2, 17, 0, 0, 0, 2, 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