Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdaf36e5d387deb09051874eafe41b463fd350a55ab6b1b8fc712775363ffda5

Tx prefix hash: 8aa9db4352f24623cad2805ed8ec730e9a900ba570814f174a2a746eca35bd40
Tx public key: b2e6efff5d5290c861e348eb13ae75e61098771e68f67dfdcd53f3bc49aef8b4
Timestamp: 1721690274 Timestamp [UCT]: 2024-07-22 23:17:54 Age [y:d:h:m:s]: 00:255:02:58:29
Block: 1071557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182253 RingCT/type: yes/0
Extra: 01b2e6efff5d5290c861e348eb13ae75e61098771e68f67dfdcd53f3bc49aef8b4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccace49e37428a35f98b1dfa8eb90f4b32bf5f2d01856a6aa8dab5ee2c0a4095 0.600000000000 1543832 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": 1071567, "vin": [ { "gen": { "height": 1071557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccace49e37428a35f98b1dfa8eb90f4b32bf5f2d01856a6aa8dab5ee2c0a4095" } } ], "extra": [ 1, 178, 230, 239, 255, 93, 82, 144, 200, 97, 227, 72, 235, 19, 174, 117, 230, 16, 152, 119, 30, 104, 246, 125, 253, 205, 83, 243, 188, 73, 174, 248, 180, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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