Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd9b4f916ff502436f68c4b2052958c5028e23ae9c9f131981e971383e7be040

Tx prefix hash: 35fb5d834ebd913c05cca3e7452776541f3d7cf06d970e7b43e5d8cf373d62ed
Tx public key: 91626b14ea243adef7d9236886043955368698b9344d7e33e4b2cbd6212b5c54
Timestamp: 1704382973 Timestamp [UCT]: 2024-01-04 15:42:53 Age [y:d:h:m:s]: 01:158:07:30:25
Block: 928087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374291 RingCT/type: yes/0
Extra: 0191626b14ea243adef7d9236886043955368698b9344d7e33e4b2cbd6212b5c540211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c6a1a24187ad7f1590e3fdf25ae67b927558ad74153ed3314e34b8bad38a6a0 0.600000000000 1385943 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": 928097, "vin": [ { "gen": { "height": 928087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c6a1a24187ad7f1590e3fdf25ae67b927558ad74153ed3314e34b8bad38a6a0" } } ], "extra": [ 1, 145, 98, 107, 20, 234, 36, 58, 222, 247, 217, 35, 104, 134, 4, 57, 85, 54, 134, 152, 185, 52, 77, 126, 51, 228, 178, 203, 214, 33, 43, 92, 84, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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