Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384ac13fe1ec9b82ab0f8a227bffad14f8db516f851ed2dd300f66eb6b69dc8a

Tx prefix hash: ea74dafe34a89ac25493a9e212c888045c8b249dfc13e7ca42891dbf23d1399b
Tx public key: a1f65b75bcbda3d7d8b522293db6fdcc7b9b7795bf5411c1deff21b5a98f1e60
Timestamp: 1658588494 Timestamp [UCT]: 2022-07-23 15:01:34 Age [y:d:h:m:s]: 03:100:16:22:37
Block: 550026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 851753 RingCT/type: yes/0
Extra: 01a1f65b75bcbda3d7d8b522293db6fdcc7b9b7795bf5411c1deff21b5a98f1e6002110000000be6d27f9c000000000000000000

1 output(s) for total of 9.237100474000 dcy

stealth address amount amount idx
00: dceb0bdc53fbe6ad384a8e1f047d0616eb54f6fd034ef126d247758e572ef94e 9.237100474000 981459 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": 550036, "vin": [ { "gen": { "height": 550026 } } ], "vout": [ { "amount": 9237100474, "target": { "key": "dceb0bdc53fbe6ad384a8e1f047d0616eb54f6fd034ef126d247758e572ef94e" } } ], "extra": [ 1, 161, 246, 91, 117, 188, 189, 163, 215, 216, 181, 34, 41, 61, 182, 253, 204, 123, 155, 119, 149, 191, 84, 17, 193, 222, 255, 33, 181, 169, 143, 30, 96, 2, 17, 0, 0, 0, 11, 230, 210, 127, 156, 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