Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eeebc02ff4a46802ef7d49433bc0d4f51cca521f92064fb1e551538d095cb0b

Tx prefix hash: ddd211d5bac2e64a97e36d32500c96f1cac51410efa53aa4fbe2bd0ed24db357
Tx public key: 5133505d2fadda353f9348f8af1ad41e79fd850ccdb9d92b9a31274fa94b9226
Timestamp: 1717068405 Timestamp [UCT]: 2024-05-30 11:26:45 Age [y:d:h:m:s]: 00:154:13:13:33
Block: 1033250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110633 RingCT/type: yes/0
Extra: 015133505d2fadda353f9348f8af1ad41e79fd850ccdb9d92b9a31274fa94b922602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7805efe19dc1c44b2bf1bbab33d71ec3f4d7b62f223e660733d382d99c4f79b 0.600000000000 1501713 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": 1033260, "vin": [ { "gen": { "height": 1033250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7805efe19dc1c44b2bf1bbab33d71ec3f4d7b62f223e660733d382d99c4f79b" } } ], "extra": [ 1, 81, 51, 80, 93, 47, 173, 218, 53, 63, 147, 72, 248, 175, 26, 212, 30, 121, 253, 133, 12, 205, 185, 217, 43, 154, 49, 39, 79, 169, 75, 146, 38, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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