Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f241e3214c59adf4bf9478d45aeda05edcc72c135cfc41b47048d137d48e00b

Tx prefix hash: ad69bb39283d09751f40dfcbdce08142818f6b58a755c8713fe2baba15c9f32b
Tx public key: 33eb7b28872ab1c481b0b576b03d6c75237595e7ec83e01d1f53f2140bb12e8a
Timestamp: 1730706327 Timestamp [UCT]: 2024-11-04 07:45:27 Age [y:d:h:m:s]: 00:141:15:37:27
Block: 1146225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101063 RingCT/type: yes/0
Extra: 0133eb7b28872ab1c481b0b576b03d6c75237595e7ec83e01d1f53f2140bb12e8a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01ff4eb6d74dc5501e48021f7a4f08ad4effc7a7bda621c7fc302e4945b19c4b 0.600000000000 1630824 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": 1146235, "vin": [ { "gen": { "height": 1146225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01ff4eb6d74dc5501e48021f7a4f08ad4effc7a7bda621c7fc302e4945b19c4b" } } ], "extra": [ 1, 51, 235, 123, 40, 135, 42, 177, 196, 129, 176, 181, 118, 176, 61, 108, 117, 35, 117, 149, 231, 236, 131, 224, 29, 31, 83, 242, 20, 11, 177, 46, 138, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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