Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 987ca000456f05b35d233a4f9fc175f38d96d08d0b5cc6e42e6c7f395200c040

Tx prefix hash: 7132ce7d8b1f3d17746bed9f0e4ec7d530a51843354942209a9a565a4ba488c8
Tx public key: 667b367df9f07844250e0338d7a55c4aee077f6f03b962c4080716a95be64c2d
Timestamp: 1763536368 Timestamp [UCT]: 2025-11-19 07:12:48 Age [y:d:h:m:s]: 00:008:23:09:42
Block: 1415365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6421 RingCT/type: yes/0
Extra: 01667b367df9f07844250e0338d7a55c4aee077f6f03b962c4080716a95be64c2d021100000002defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48df60c9778579279b3e79c1b18f57b1579a09fc1147ceb1a083caf123ac9840 0.600000000000 1903866 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": 1415375, "vin": [ { "gen": { "height": 1415365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48df60c9778579279b3e79c1b18f57b1579a09fc1147ceb1a083caf123ac9840" } } ], "extra": [ 1, 102, 123, 54, 125, 249, 240, 120, 68, 37, 14, 3, 56, 215, 165, 92, 74, 238, 7, 127, 111, 3, 185, 98, 196, 8, 7, 22, 169, 91, 230, 76, 45, 2, 17, 0, 0, 0, 2, 222, 251, 143, 24, 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