Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6592cad8fe9b581f40e8854c42a7f7f30662a77a53271fb07f92699c6ec4a717

Tx prefix hash: 9408e6c387a3c746abe88f650bd56dd897a0f135587a63e04eff6aca1665500b
Tx public key: a5a251f19f57d9e3f2d17d994466bc9be5a692bd125cd1cfcf384fb6f32dcaf8
Timestamp: 1708972760 Timestamp [UCT]: 2024-02-26 18:39:20 Age [y:d:h:m:s]: 01:033:10:34:10
Block: 966143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284900 RingCT/type: yes/0
Extra: 01a5a251f19f57d9e3f2d17d994466bc9be5a692bd125cd1cfcf384fb6f32dcaf802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfe4824d948cd755ce42594dd50bd3e414de15934a57fd2a97fd384bf026182a 0.600000000000 1425900 of 15

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": 966153, "vin": [ { "gen": { "height": 966143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfe4824d948cd755ce42594dd50bd3e414de15934a57fd2a97fd384bf026182a" } } ], "extra": [ 1, 165, 162, 81, 241, 159, 87, 217, 227, 242, 209, 125, 153, 68, 102, 188, 155, 229, 166, 146, 189, 18, 92, 209, 207, 207, 56, 79, 182, 243, 45, 202, 248, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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