Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7ee6371adcb3d4ec7073bd94315b27683ff429ad4aacc19d5b5995e52525db

Tx prefix hash: 85f84526fcbe95c90bd4bbc67209b061919002e0f7fc5669da6d468e34d7421b
Tx public key: 94e2401fe251eb3312d291e30c68159917d961d4137a907fc7608b66f0f9e41b
Timestamp: 1715552170 Timestamp [UCT]: 2024-05-12 22:16:10 Age [y:d:h:m:s]: 00:309:05:20:10
Block: 1020712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220992 RingCT/type: yes/0
Extra: 0194e2401fe251eb3312d291e30c68159917d961d4137a907fc7608b66f0f9e41b021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 318b7a38afffafd9e6fd2732616364fb64f78a6027f9986b0c60d839677ef2b5 0.600000000000 1484793 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": 1020722, "vin": [ { "gen": { "height": 1020712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "318b7a38afffafd9e6fd2732616364fb64f78a6027f9986b0c60d839677ef2b5" } } ], "extra": [ 1, 148, 226, 64, 31, 226, 81, 235, 51, 18, 210, 145, 227, 12, 104, 21, 153, 23, 217, 97, 212, 19, 122, 144, 127, 199, 96, 139, 102, 240, 249, 228, 27, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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