Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4010cea31949c2e04ded235416a71cc886b350aadad4076c8db9de94fa7b869e

Tx prefix hash: fa7b00031512f942c100127db0cb29d35ea81d95af28f75504e2bf211ce2120e
Tx public key: ddc8e965603d03f7a4f30c9df4ba4a262160d0a494e40b8da6bd3b12aab808d6
Timestamp: 1754570154 Timestamp [UCT]: 2025-08-07 12:35:54 Age [y:d:h:m:s]: 00:094:15:36:19
Block: 1342122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66714 RingCT/type: yes/0
Extra: 01ddc8e965603d03f7a4f30c9df4ba4a262160d0a494e40b8da6bd3b12aab808d60211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eda5f0642ca5ab8d727e59a1afbfc62da7fa4ccac226be2f316a0518d92d526c 0.600000000000 1829951 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": 1342132, "vin": [ { "gen": { "height": 1342122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eda5f0642ca5ab8d727e59a1afbfc62da7fa4ccac226be2f316a0518d92d526c" } } ], "extra": [ 1, 221, 200, 233, 101, 96, 61, 3, 247, 164, 243, 12, 157, 244, 186, 74, 38, 33, 96, 208, 164, 148, 228, 11, 141, 166, 189, 59, 18, 170, 184, 8, 214, 2, 17, 0, 0, 0, 2, 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