Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5260f387c48dce32b6663bbcefb4fcc129d9d706ec7cd470c06098b85a8504fd

Tx prefix hash: 1fb46a943ffc3c7f9d94a4af97f50e70de055b381251bb87781974689ebf5e32
Tx public key: 9430f79f9efec170b0b97f95616b5ed7645f87ce97e8d598e6745c60b7da3ad4
Timestamp: 1711486421 Timestamp [UCT]: 2024-03-26 20:53:41 Age [y:d:h:m:s]: 01:088:10:55:52
Block: 987002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324002 RingCT/type: yes/0
Extra: 019430f79f9efec170b0b97f95616b5ed7645f87ce97e8d598e6745c60b7da3ad402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9452b805251eaac79a4c37969eb66e8a848b8972f305b6fba6928113fc7a7e5b 0.600000000000 1447241 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": 987012, "vin": [ { "gen": { "height": 987002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9452b805251eaac79a4c37969eb66e8a848b8972f305b6fba6928113fc7a7e5b" } } ], "extra": [ 1, 148, 48, 247, 159, 158, 254, 193, 112, 176, 185, 127, 149, 97, 107, 94, 215, 100, 95, 135, 206, 151, 232, 213, 152, 230, 116, 92, 96, 183, 218, 58, 212, 2, 17, 0, 0, 0, 4, 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