Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d72a66f06fcb463fa7cc1cb7216108662e41e1c54b6731bbfe9f5a75322fbcd

Tx prefix hash: fbc6b1a9134f05362a886ed9a12a705e62368448bb8fdf48a9b4a5811662f480
Tx public key: 7aef15f05bae77e289602ed5a3762008cc76cfdcab7a4d8f434abee0f2c946e9
Timestamp: 1750390884 Timestamp [UCT]: 2025-06-20 03:41:24 Age [y:d:h:m:s]: 00:153:04:20:05
Block: 1308804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107301 RingCT/type: yes/0
Extra: 017aef15f05bae77e289602ed5a3762008cc76cfdcab7a4d8f434abee0f2c946e90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 320f2a0d8b8364998469fa3df43e947fe1d643f9aa4c65a109747126867842bc 0.600000000000 1796419 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": 1308814, "vin": [ { "gen": { "height": 1308804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "320f2a0d8b8364998469fa3df43e947fe1d643f9aa4c65a109747126867842bc" } } ], "extra": [ 1, 122, 239, 21, 240, 91, 174, 119, 226, 137, 96, 46, 213, 163, 118, 32, 8, 204, 118, 207, 220, 171, 122, 77, 143, 67, 74, 190, 224, 242, 201, 70, 233, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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