Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ad426c7b6251536c9cb300293d10a5736a2f9ec85fd06c804d0a907b9337e36

Tx prefix hash: 9f2c5ac96c41b1bb6b794589493210e2a20ff28dbe1891a3df14d10f5ee33d50
Tx public key: 052fe91ddad0b4b8988042a91532b3d400a7dcf07e4faa6ba7c3212ebf9ab692
Timestamp: 1744858957 Timestamp [UCT]: 2025-04-17 03:02:37 Age [y:d:h:m:s]: 00:218:04:42:13
Block: 1263133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153666 RingCT/type: yes/0
Extra: 01052fe91ddad0b4b8988042a91532b3d400a7dcf07e4faa6ba7c3212ebf9ab692021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c4277f7a621b9192b2fa83485f5961aa3470e59f9a09122f11be4343636a8de 0.600000000000 1750316 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": 1263143, "vin": [ { "gen": { "height": 1263133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c4277f7a621b9192b2fa83485f5961aa3470e59f9a09122f11be4343636a8de" } } ], "extra": [ 1, 5, 47, 233, 29, 218, 208, 180, 184, 152, 128, 66, 169, 21, 50, 179, 212, 0, 167, 220, 240, 126, 79, 170, 107, 167, 195, 33, 46, 191, 154, 182, 146, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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