Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffb93f32bbc438620f51cca3c5a0ac82e37c6bc9e82d04d06401b9f7c1ec52a4

Tx prefix hash: 9391bf4ca86909426f4dd97e460a7e4064c8f7274ae3ddf4bed6f9e260d47fe1
Tx public key: 99d7f6dae46353fcd1d35a0f02f8f3fb57ac31ccf51525ce044efa2a3354cc21
Timestamp: 1577366533 Timestamp [UCT]: 2019-12-26 13:22:13 Age [y:d:h:m:s]: 05:003:21:24:41
Block: 32192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152769 RingCT/type: yes/0
Extra: 0199d7f6dae46353fcd1d35a0f02f8f3fb57ac31ccf51525ce044efa2a3354cc210211000000034943cd9f000000000000000000

1 output(s) for total of 480.128943151000 dcy

stealth address amount amount idx
00: 4baecfe04bc5564280391152af2a56171e62e61aee304d90d2ae0abc16392f9f 480.128943151000 53474 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": 32202, "vin": [ { "gen": { "height": 32192 } } ], "vout": [ { "amount": 480128943151, "target": { "key": "4baecfe04bc5564280391152af2a56171e62e61aee304d90d2ae0abc16392f9f" } } ], "extra": [ 1, 153, 215, 246, 218, 228, 99, 83, 252, 209, 211, 90, 15, 2, 248, 243, 251, 87, 172, 49, 204, 245, 21, 37, 206, 4, 78, 250, 42, 51, 84, 204, 33, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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