Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00fb50d6acfb7581f77014363575bda2f0bbb97e491f514f678a2c9b24eba466

Tx prefix hash: 56d3c54c53f75cd5c74bd3005ad2d8767f35cbc37ea1840113a7153e0ba05c5f
Tx public key: 8f34fd46eb2d78ca587c22fad697dfa54fabbe23cf92644404f3f8af3a2f53f5
Timestamp: 1719004797 Timestamp [UCT]: 2024-06-21 21:19:57 Age [y:d:h:m:s]: 00:324:03:54:39
Block: 1049278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231685 RingCT/type: yes/0
Extra: 018f34fd46eb2d78ca587c22fad697dfa54fabbe23cf92644404f3f8af3a2f53f502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6efda3d3f712cead5726aa29d2e3be4e01e31d0e37d857f54fbe1cd14710a75d 0.600000000000 1519377 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": 1049288, "vin": [ { "gen": { "height": 1049278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6efda3d3f712cead5726aa29d2e3be4e01e31d0e37d857f54fbe1cd14710a75d" } } ], "extra": [ 1, 143, 52, 253, 70, 235, 45, 120, 202, 88, 124, 34, 250, 214, 151, 223, 165, 79, 171, 190, 35, 207, 146, 100, 68, 4, 243, 248, 175, 58, 47, 83, 245, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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