Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c4b470253591062cef96ae9f93369799da691b649863bddbea5216fd72da253

Tx prefix hash: c9bb5b5f0137a23768fcbacaa7f9327c8e40b2f7cd8b2ae77934333cd0bdead7
Tx public key: 0fb591d8a0067333e6f67699b7aab60fc3e5a03a6e65b1409d9679c2367bc64f
Timestamp: 1732396662 Timestamp [UCT]: 2024-11-23 21:17:42 Age [y:d:h:m:s]: 00:129:09:02:18
Block: 1160231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92267 RingCT/type: yes/0
Extra: 010fb591d8a0067333e6f67699b7aab60fc3e5a03a6e65b1409d9679c2367bc64f0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4afb9df47c31b68454a5a55485e46bca26d477059f7853808a8e010bc98fcedb 0.600000000000 1645874 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": 1160241, "vin": [ { "gen": { "height": 1160231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4afb9df47c31b68454a5a55485e46bca26d477059f7853808a8e010bc98fcedb" } } ], "extra": [ 1, 15, 181, 145, 216, 160, 6, 115, 51, 230, 246, 118, 153, 183, 170, 182, 15, 195, 229, 160, 58, 110, 101, 177, 64, 157, 150, 121, 194, 54, 123, 198, 79, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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