Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7533588af03a69993d1042fe9a5b226d732e4f81d10b25bfe532cbf05b856b1a

Tx prefix hash: 0af6b8e579c5aed70afe28720e7dec99690ba6e016b00d899e841ca723e9d3a9
Tx public key: cd8cb33510a84a8ec6b31aa7152076acabcb235007192b130db7b68aafecaa05
Timestamp: 1723477605 Timestamp [UCT]: 2024-08-12 15:46:45 Age [y:d:h:m:s]: 00:231:09:27:56
Block: 1086386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165252 RingCT/type: yes/0
Extra: 01cd8cb33510a84a8ec6b31aa7152076acabcb235007192b130db7b68aafecaa05021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3abae9d1da593577a5a70ca7b408373b75939674f264d811b27cbd917f1c7cc8 0.600000000000 1560983 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": 1086396, "vin": [ { "gen": { "height": 1086386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3abae9d1da593577a5a70ca7b408373b75939674f264d811b27cbd917f1c7cc8" } } ], "extra": [ 1, 205, 140, 179, 53, 16, 168, 74, 142, 198, 179, 26, 167, 21, 32, 118, 172, 171, 203, 35, 80, 7, 25, 43, 19, 13, 183, 182, 138, 175, 236, 170, 5, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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