Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d93c15a61b6301608fde2a2d56e9f23a829a4901ef09621a46ee902af1ff562

Tx prefix hash: a874f53aaad6b1855f09c313adf15d61fc34e628dcc300548070bdf4b396165e
Tx public key: b27d1e8805e90b86e83a94b1338289ab78d53a7dced3f10acd4791b5932fe166
Timestamp: 1578740289 Timestamp [UCT]: 2020-01-11 10:58:09 Age [y:d:h:m:s]: 04:353:03:25:09
Block: 43208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141851 RingCT/type: yes/0
Extra: 01b27d1e8805e90b86e83a94b1338289ab78d53a7dced3f10acd4791b5932fe1660211000000054ac5aa02000000000000000000

1 output(s) for total of 441.402514092000 dcy

stealth address amount amount idx
00: cbab4ee47f5fa3254d510ba64a6be6969e5de665943bc66e8ad18f0eac258178 441.402514092000 78143 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": 43218, "vin": [ { "gen": { "height": 43208 } } ], "vout": [ { "amount": 441402514092, "target": { "key": "cbab4ee47f5fa3254d510ba64a6be6969e5de665943bc66e8ad18f0eac258178" } } ], "extra": [ 1, 178, 125, 30, 136, 5, 233, 11, 134, 232, 58, 148, 177, 51, 130, 137, 171, 120, 213, 58, 125, 206, 211, 241, 10, 205, 71, 145, 181, 147, 47, 225, 102, 2, 17, 0, 0, 0, 5, 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