Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4066466ef44501ab3a7f5e0880f8842965187c83e07a224ffd205d331659f566

Tx prefix hash: f5f0a321077cf1ed86729d983a7639ce40e2b1295eee5ed2c2aebb74ec0aec2e
Tx public key: d42587f322927bdc30c4eb18286dcec46ccc5fa9b39b581b753a16e0f1ab6a70
Timestamp: 1696845411 Timestamp [UCT]: 2023-10-09 09:56:51 Age [y:d:h:m:s]: 01:017:04:29:46
Block: 865803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273511 RingCT/type: yes/0
Extra: 01d42587f322927bdc30c4eb18286dcec46ccc5fa9b39b581b753a16e0f1ab6a7002110000000c4b8f5122000000000000000000

1 output(s) for total of 0.830300468000 dcy

stealth address amount amount idx
00: 45fed0365128500523a28184874353f98d7c8d027423dbf0f107173f7b19752a 0.830300468000 1320353 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": 865813, "vin": [ { "gen": { "height": 865803 } } ], "vout": [ { "amount": 830300468, "target": { "key": "45fed0365128500523a28184874353f98d7c8d027423dbf0f107173f7b19752a" } } ], "extra": [ 1, 212, 37, 135, 243, 34, 146, 123, 220, 48, 196, 235, 24, 40, 109, 206, 196, 108, 204, 95, 169, 179, 155, 88, 27, 117, 58, 22, 224, 241, 171, 106, 112, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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