Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394c99af96e5bb3c713128f4a89be5ba19fac9cfde5f07858da0e7a59bf472e3

Tx prefix hash: 3827fa1e64f71625142496271e2cb30f8340dfbb97ee7d041089ca46f7f3f710
Tx public key: fa59463683cd3e960809c5f9a621428f5327dda8f490b28b32c7a4cf96eca5f8
Timestamp: 1728971396 Timestamp [UCT]: 2024-10-15 05:49:56 Age [y:d:h:m:s]: 01:023:12:36:45
Block: 1131933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275176 RingCT/type: yes/0
Extra: 01fa59463683cd3e960809c5f9a621428f5327dda8f490b28b32c7a4cf96eca5f8021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 970336c264b7d3c3f3a4f3a2088c4a7da5b85f5c30e2090f5d8b73c308f6e7bc 0.600000000000 1614842 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": 1131943, "vin": [ { "gen": { "height": 1131933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "970336c264b7d3c3f3a4f3a2088c4a7da5b85f5c30e2090f5d8b73c308f6e7bc" } } ], "extra": [ 1, 250, 89, 70, 54, 131, 205, 62, 150, 8, 9, 197, 249, 166, 33, 66, 143, 83, 39, 221, 168, 244, 144, 178, 139, 50, 199, 164, 207, 150, 236, 165, 248, 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