Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a530a401825981607b49c4a18a4c20bb1a66f94ac63b7f89516844fabd2559bf

Tx prefix hash: 64efc592cdcf016f2e60b4ba3b26c5dc4f7287c775fef7f5f2766211add62a6c
Tx public key: 786f8f65093e6dd7a82a801732d171107a8e0294e1b0348c23c5471f75518ef1
Timestamp: 1714564157 Timestamp [UCT]: 2024-05-01 11:49:17 Age [y:d:h:m:s]: 00:302:20:58:50
Block: 1012492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216470 RingCT/type: yes/0
Extra: 01786f8f65093e6dd7a82a801732d171107a8e0294e1b0348c23c5471f75518ef102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd0ba4197c40791e5a64b9b89a17cb7009d3bfdc08dacf9dc0fe9e9da37c8363 0.600000000000 1475038 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": 1012502, "vin": [ { "gen": { "height": 1012492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd0ba4197c40791e5a64b9b89a17cb7009d3bfdc08dacf9dc0fe9e9da37c8363" } } ], "extra": [ 1, 120, 111, 143, 101, 9, 62, 109, 215, 168, 42, 128, 23, 50, 209, 113, 16, 122, 142, 2, 148, 225, 176, 52, 140, 35, 197, 71, 31, 117, 81, 142, 241, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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