Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e756a95a1351e9c6fca114522af1e10c09f49868405d32f2ec7678be1cd6dabc

Tx prefix hash: 1401babde2b33d66001f32f4842c7cb580ecdd0eed7ec23082f75eb52602fbd5
Tx public key: 829e89be39b1c3f4514bb7cf3813925dca240e3dd16043e56f7ad46618aab4f9
Timestamp: 1580263029 Timestamp [UCT]: 2020-01-29 01:57:09 Age [y:d:h:m:s]: 04:304:00:27:30
Block: 54263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108267 RingCT/type: yes/0
Extra: 01829e89be39b1c3f4514bb7cf3813925dca240e3dd16043e56f7ad46618aab4f9021100000003b221b3d1000000000000000000

1 output(s) for total of 405.699976075000 dcy

stealth address amount amount idx
00: 93de682e2f102e6d8e6d1c83a28ce096bc3beca6ad91240f2f40140a6c96a015 405.699976075000 100595 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": 54273, "vin": [ { "gen": { "height": 54263 } } ], "vout": [ { "amount": 405699976075, "target": { "key": "93de682e2f102e6d8e6d1c83a28ce096bc3beca6ad91240f2f40140a6c96a015" } } ], "extra": [ 1, 130, 158, 137, 190, 57, 177, 195, 244, 81, 75, 183, 207, 56, 19, 146, 93, 202, 36, 14, 61, 209, 96, 67, 229, 111, 122, 212, 102, 24, 170, 180, 249, 2, 17, 0, 0, 0, 3, 178, 33, 179, 209, 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