Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a29f49431dfee3fed6b9b89276b47c371f7f8b18f416835f777b85ac6ffd8d2a

Tx prefix hash: 8d480c7715ccfa2b282415cc28c767cd5a5aa81f22814dd4dfff586d54130f2c
Tx public key: 7c22f3e045b8266c05394acb947119c48dbe2961de36bbad7d6fe725d534e88c
Timestamp: 1755504516 Timestamp [UCT]: 2025-08-18 08:08:36 Age [y:d:h:m:s]: 00:093:08:53:07
Block: 1349061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66597 RingCT/type: yes/0
Extra: 017c22f3e045b8266c05394acb947119c48dbe2961de36bbad7d6fe725d534e88c0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 879f9241c6f2b9e6526d77a4f7eee430ee5bb3844edd7e6936c0ad330a28a019 0.600000000000 1836992 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": 1349071, "vin": [ { "gen": { "height": 1349061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "879f9241c6f2b9e6526d77a4f7eee430ee5bb3844edd7e6936c0ad330a28a019" } } ], "extra": [ 1, 124, 34, 243, 224, 69, 184, 38, 108, 5, 57, 74, 203, 148, 113, 25, 196, 141, 190, 41, 97, 222, 54, 187, 173, 125, 111, 231, 37, 213, 52, 232, 140, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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