Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 616565df99f33fb1363b5c43304b67e94c4f703e6b49cb61c1cb4ae2588eb738

Tx prefix hash: 4b9bdb7c88aef954bd1b5debc1e9f18bf3290b359bb55813d0059a4d6e859e62
Tx public key: 41198d4899a631e88a572016f54f65d920f162e8873f66674a0a591489f6c111
Timestamp: 1704622241 Timestamp [UCT]: 2024-01-07 10:10:41 Age [y:d:h:m:s]: 01:089:23:39:28
Block: 930048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325431 RingCT/type: yes/0
Extra: 0141198d4899a631e88a572016f54f65d920f162e8873f66674a0a591489f6c11102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a2d34983e2f4161bd9063006a71ea2972af89be73381d6fd82e48978e0375e4 0.600000000000 1387926 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": 930058, "vin": [ { "gen": { "height": 930048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2d34983e2f4161bd9063006a71ea2972af89be73381d6fd82e48978e0375e4" } } ], "extra": [ 1, 65, 25, 141, 72, 153, 166, 49, 232, 138, 87, 32, 22, 245, 79, 101, 217, 32, 241, 98, 232, 135, 63, 102, 103, 74, 10, 89, 20, 137, 246, 193, 17, 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