Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea03dc2384e1abb45f96c1a186ad122dd1134ad0aadbbb1811cb5959d6363202

Tx prefix hash: e1f7c6d240394f13bffba99a92a188ab51e3e4aaea85b5cc944e414fe8146dac
Tx public key: 7453a58df6e299aae27445720f40e514be0aa36377d20e16208e6aadafe5700b
Timestamp: 1720286142 Timestamp [UCT]: 2024-07-06 17:15:42 Age [y:d:h:m:s]: 00:270:15:43:55
Block: 1059923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193373 RingCT/type: yes/0
Extra: 017453a58df6e299aae27445720f40e514be0aa36377d20e16208e6aadafe5700b0211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 196c837c352e70627137e1c9dfb69a5b35dd07a137f563143484c6c2ba418de6 0.600000000000 1530394 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": 1059933, "vin": [ { "gen": { "height": 1059923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "196c837c352e70627137e1c9dfb69a5b35dd07a137f563143484c6c2ba418de6" } } ], "extra": [ 1, 116, 83, 165, 141, 246, 226, 153, 170, 226, 116, 69, 114, 15, 64, 229, 20, 190, 10, 163, 99, 119, 210, 14, 22, 32, 142, 106, 173, 175, 229, 112, 11, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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