Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32c0e34b21f6d38ecfad17361d26a07f049ec3c8225322163aa2862ba59ba45b

Tx prefix hash: 44860fc948cf1211cda706dc00a64881cf51d44514bd9ad2956bc860374683fe
Tx public key: 9b24a748348b4b74d0f1281f527091b2c76c7e3abc5b455e1f142b18ef496860
Timestamp: 1750235085 Timestamp [UCT]: 2025-06-18 08:24:45 Age [y:d:h:m:s]: 00:151:11:03:38
Block: 1307535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106048 RingCT/type: yes/0
Extra: 019b24a748348b4b74d0f1281f527091b2c76c7e3abc5b455e1f142b18ef49686002110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afda1f499d55a673d8a75299bcfe1e6ff709d8d3ada001f6b29eadbc5b23e429 0.600000000000 1795146 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": 1307545, "vin": [ { "gen": { "height": 1307535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afda1f499d55a673d8a75299bcfe1e6ff709d8d3ada001f6b29eadbc5b23e429" } } ], "extra": [ 1, 155, 36, 167, 72, 52, 139, 75, 116, 208, 241, 40, 31, 82, 112, 145, 178, 199, 108, 126, 58, 188, 91, 69, 94, 31, 20, 43, 24, 239, 73, 104, 96, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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