Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeebcc8647649260558c73933fbc221c3002e0a252e9bf626cbd4ed905b2e969

Tx prefix hash: 070e16bab2671dc7084eb45e8ca3b52bdfbb372f092bd66ee194cc761ca5f304
Tx public key: 43b5510fddf9f8d7212820c7a2b77f213b899f685ed92daeee0b4a2090edb2ab
Timestamp: 1577776810 Timestamp [UCT]: 2019-12-31 07:20:10 Age [y:d:h:m:s]: 05:065:12:26:30
Block: 35529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196644 RingCT/type: yes/0
Extra: 0143b5510fddf9f8d7212820c7a2b77f213b899f685ed92daeee0b4a2090edb2ab0211000000074ac5aa02000000000000000000

1 output(s) for total of 468.035212571000 dcy

stealth address amount amount idx
00: 66a7a8c1b402ed9d8d2cdd917328e6f31dbc9dc413e5e8ec9ef0209cecc6e7c9 468.035212571000 59970 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": 35539, "vin": [ { "gen": { "height": 35529 } } ], "vout": [ { "amount": 468035212571, "target": { "key": "66a7a8c1b402ed9d8d2cdd917328e6f31dbc9dc413e5e8ec9ef0209cecc6e7c9" } } ], "extra": [ 1, 67, 181, 81, 15, 221, 249, 248, 215, 33, 40, 32, 199, 162, 183, 127, 33, 59, 137, 159, 104, 94, 217, 45, 174, 238, 11, 74, 32, 144, 237, 178, 171, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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