Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d7c6d509f9e04062573af65732fad9a9163af7a6f82cee51ec494476c7f9d56

Tx prefix hash: 747c42d5f8c87cebc0794d2edc53159b6eefdfc4cd8e145cdf3753d10d61b44d
Tx public key: 12b71d16c902920d25e4f171be4e4653eed91e8495d8e37ba4036a8099336297
Timestamp: 1752467835 Timestamp [UCT]: 2025-07-14 04:37:15 Age [y:d:h:m:s]: 00:202:05:49:34
Block: 1325079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143186 RingCT/type: yes/0
Extra: 0112b71d16c902920d25e4f171be4e4653eed91e8495d8e37ba4036a8099336297021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91b7d8fe9b39a28a7f28cd6819ff7fa9dd6ffabd01dcaf814a0c220ea74a7f5c 0.600000000000 1812824 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": 1325089, "vin": [ { "gen": { "height": 1325079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91b7d8fe9b39a28a7f28cd6819ff7fa9dd6ffabd01dcaf814a0c220ea74a7f5c" } } ], "extra": [ 1, 18, 183, 29, 22, 201, 2, 146, 13, 37, 228, 241, 113, 190, 78, 70, 83, 238, 217, 30, 132, 149, 216, 227, 123, 164, 3, 106, 128, 153, 51, 98, 151, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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