Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71078023c61792c8fbe4a0c35c782e20495b5cd63ffd76d0ccc865434fbb7983

Tx prefix hash: 3c93c3e2c619a128b333a83b268c31366a0a2eee75d8c3f1069f661e6c080e3f
Tx public key: 857116ddac268a64f28b9dba2c39c5f48d48d6769e99b24cf081f1674b900889
Timestamp: 1758693665 Timestamp [UCT]: 2025-09-24 06:01:05 Age [y:d:h:m:s]: 00:103:16:51:31
Block: 1375224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74286 RingCT/type: yes/0
Extra: 01857116ddac268a64f28b9dba2c39c5f48d48d6769e99b24cf081f1674b900889021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce2c7d63902df488adf0e899f0d708231d23dc590cd8a17fe4c94f7f36f373f1 0.600000000000 1863309 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": 1375234, "vin": [ { "gen": { "height": 1375224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce2c7d63902df488adf0e899f0d708231d23dc590cd8a17fe4c94f7f36f373f1" } } ], "extra": [ 1, 133, 113, 22, 221, 172, 38, 138, 100, 242, 139, 157, 186, 44, 57, 197, 244, 141, 72, 214, 118, 158, 153, 178, 76, 240, 129, 241, 103, 75, 144, 8, 137, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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