Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 924a9aee4480d5d1a0ba49db45d3cd7555473480ffd4cc85739d1faf8049f5e6

Tx prefix hash: 1678f257dce7f135814c458a1fcc216baa1ab1d272971e610d35bc4de8687644
Tx public key: a7e560656c30a4e2780f64fb43cfeed4edaee1e6cc70f8090804f5d8741a1670
Timestamp: 1707922358 Timestamp [UCT]: 2024-02-14 14:52:38 Age [y:d:h:m:s]: 01:054:14:26:04
Block: 957417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300063 RingCT/type: yes/0
Extra: 01a7e560656c30a4e2780f64fb43cfeed4edaee1e6cc70f8090804f5d8741a16700211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 806412f84811cc82db087d3d0ae1c37a3b44b997d8c0bc6d393b2eab976221f7 0.600000000000 1416735 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": 957427, "vin": [ { "gen": { "height": 957417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "806412f84811cc82db087d3d0ae1c37a3b44b997d8c0bc6d393b2eab976221f7" } } ], "extra": [ 1, 167, 229, 96, 101, 108, 48, 164, 226, 120, 15, 100, 251, 67, 207, 238, 212, 237, 174, 225, 230, 204, 112, 248, 9, 8, 4, 245, 216, 116, 26, 22, 112, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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