Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e78813bdfbb81560df11a0acd96daa6c290953189f4ef36220dd27457f92f81

Tx prefix hash: abbc63b1ca02f7cc3b7c3a84d2bef17b449785a0b81b34ebf998de13f99773a0
Tx public key: 0e6f2031d438a29e35bf69fc67e4b224924b9db82ffd06ae9f1f387ba4a7e2e9
Timestamp: 1755927375 Timestamp [UCT]: 2025-08-23 05:36:15 Age [y:d:h:m:s]: 00:085:11:56:48
Block: 1352483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61042 RingCT/type: yes/0
Extra: 010e6f2031d438a29e35bf69fc67e4b224924b9db82ffd06ae9f1f387ba4a7e2e90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f435e804cf4421493603a53838a769592790613f0df87ade7a8321d943c4b1de 0.600000000000 1840448 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": 1352493, "vin": [ { "gen": { "height": 1352483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f435e804cf4421493603a53838a769592790613f0df87ade7a8321d943c4b1de" } } ], "extra": [ 1, 14, 111, 32, 49, 212, 56, 162, 158, 53, 191, 105, 252, 103, 228, 178, 36, 146, 75, 157, 184, 47, 253, 6, 174, 159, 31, 56, 123, 164, 167, 226, 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