Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cb89fd8e73aa569efd031c21f7b554e81d2eb8034dc699e057d7db36e4af43e

Tx prefix hash: 2e430f31d57cd66a2e441e93de1e163b691681742df8f176467a237556ff72bc
Tx public key: 8678c1dbfe89f1973361c548cf718f750ab303dfd29f16e77e8a159c4a1dc110
Timestamp: 1703402521 Timestamp [UCT]: 2023-12-24 07:22:01 Age [y:d:h:m:s]: 01:095:10:59:32
Block: 919952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329341 RingCT/type: yes/0
Extra: 018678c1dbfe89f1973361c548cf718f750ab303dfd29f16e77e8a159c4a1dc1100211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94d1feee4ca61d49f9bc79fd51463df80c042c22723bb3c4c8ac051633dbc304 0.600000000000 1377630 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": 919962, "vin": [ { "gen": { "height": 919952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94d1feee4ca61d49f9bc79fd51463df80c042c22723bb3c4c8ac051633dbc304" } } ], "extra": [ 1, 134, 120, 193, 219, 254, 137, 241, 151, 51, 97, 197, 72, 207, 113, 143, 117, 10, 179, 3, 223, 210, 159, 22, 231, 126, 138, 21, 156, 74, 29, 193, 16, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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