Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 437f1af13c91c44916694bf49f91ce6bc57d7f4ae966097eaa47146c50bd62fd

Tx prefix hash: 1ab9e9eec3d804a4c80e1c8ff9c3d1dd0a48cc74adf347a93e1b24da0ac8fa01
Tx public key: cb7f3f64fdf234bca32528f7c91897fe4c4b191a30c58e58b5aa2ab3c78b6505
Timestamp: 1721737128 Timestamp [UCT]: 2024-07-23 12:18:48 Age [y:d:h:m:s]: 00:258:01:44:47
Block: 1071948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184368 RingCT/type: yes/0
Extra: 01cb7f3f64fdf234bca32528f7c91897fe4c4b191a30c58e58b5aa2ab3c78b6505021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa2bfc85d18925753cbc060cda3c7454bff840172ef219af8d4255fa177a080f 0.600000000000 1544355 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": 1071958, "vin": [ { "gen": { "height": 1071948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa2bfc85d18925753cbc060cda3c7454bff840172ef219af8d4255fa177a080f" } } ], "extra": [ 1, 203, 127, 63, 100, 253, 242, 52, 188, 163, 37, 40, 247, 201, 24, 151, 254, 76, 75, 25, 26, 48, 197, 142, 88, 181, 170, 42, 179, 199, 139, 101, 5, 2, 17, 0, 0, 0, 3, 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